Skip to content

[Snyk] Security upgrade com.microsoft.sqlserver:mssql-jdbc from 12.8.1.jre11 to 12.8.2.jre8#526

Open
ISGA wants to merge 1 commit intomainfrom
snyk-fix-ab70ac3f0091d1822720875dced192d9
Open

[Snyk] Security upgrade com.microsoft.sqlserver:mssql-jdbc from 12.8.1.jre11 to 12.8.2.jre8#526
ISGA wants to merge 1 commit intomainfrom
snyk-fix-ab70ac3f0091d1822720875dced192d9

Conversation

@ISGA
Copy link
Copy Markdown
Owner

@ISGA ISGA commented Nov 9, 2025

User description

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Improper Validation of Certificate with Host Mismatch
SNYK-JAVA-COMMICROSOFTSQLSERVER-13821835
  187   com.microsoft.sqlserver:mssql-jdbc:
12.8.1.jre11 -> 12.8.2.jre8
No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


CodeAnt-AI Description

Update MS SQL JDBC driver to fix certificate host-mismatch vulnerability

What Changed

  • MS SQL JDBC driver upgraded from 12.8.1.jre11 to 12.8.2.jre8 to address an improper certificate validation (host mismatch) security issue
  • Removed an empty contributors element from project metadata (pom.xml cleanup)

Impact

✅ Fewer DB TLS host-mismatch vulnerabilities
✅ Lower risk of man-in-the-middle on MS SQL connections
✅ Cleaner project metadata

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@codeant-ai
Copy link
Copy Markdown
Contributor

codeant-ai bot commented Nov 9, 2025

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@amplify-security
Copy link
Copy Markdown
Contributor

🔍 Amplify code check status:   status looks good

⚠️ 0 issues detected in   📄 1 file and   ❇️ 4 lines of code   🛠️ using Opengrep

Last updated by commit ab0c521 at 2025-11-09 08:58:51 UTC.

@codeant-ai codeant-ai bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Nov 9, 2025
@zeropath-ai
Copy link
Copy Markdown

zeropath-ai bot commented Nov 9, 2025

🟡 Security issue(s) detected below the blocking threshold. Reviewed everything up to ab0c521.

The following issues were found:

Security Overview
Detected Code Changes
Change Type Relevant files
Configuration changes ► pom.xml
    Update mssql-jdbc.version to 12.8.2.jre8
    Remove content from contributors tag

Reply to this PR with @zeropath-ai followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

@codeant-ai
Copy link
Copy Markdown
Contributor

codeant-ai bot commented Nov 9, 2025

CodeAnt AI finished reviewing your PR.

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: Undertow client not checking server identity presented by server certificate in https connections in maven io.undertow:undertow-core

CVE: GHSA-pfcc-3g6r-8rg8 Undertow client not checking server identity presented by server certificate in https connections (CRITICAL)

Affected versions: >= 2.3.0 < 2.3.5.Final; < 2.2.24.Final

Patched version: 2.3.5.Final

From: pom.xmlmaven/org.jboss.arquillian.container/undertow-embedded@1.0.0.Finalmaven/io.undertow/undertow-core@2.3.3.Final

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/io.undertow/undertow-core@2.3.3.Final. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants